Suggested uses for generic precedences are:
(examples given in ()'s)
In main_prec:
Inpreop 1 arg term with prefix text (not, minus, squash)
Inpostop 1 arg term with postfix text (pi1, pi2)
Ininop 2 arg term with infix text (compose, append)
Inwk_preop term with prefix and maybe infix text (mon_reduce)
Inwk_postop term with postfix and maybe infix text
Inbd_preop term with prefix and maybe infix text (exists, for, lambda)
Inbd_postop term with postfix and maybe infix text
InThe bd_*op are intended for terms that bind 1 or more variables in their
Inrightmost argument. Having these weak precedences corresponds with
Inthe convention that common binding terms have maximal scope.
InThe exposed slot of pre and postop terms (including wk_* and bd_*) should
Inhave E paren control so that ops can be stacked without adding
Inparenthesization.
Interms that use inop should use the infix_df_gen display form generator from
Inthe boot theory. This uses iteration control to suppress parenthesization of
Inright associated term rather than E paren control, since then multiple
Indfs can use inop and will always be parenthesized when nested inside
Inone another.
In logic_prec:
Inatomrel: atomic relations with infix and maybe postfix text (equal, member, lt)
A good place to add pointers to new auxiliary precedence objects is
in parallel with *arith_prec*.